From 405c1c7e9b3e4d488dd85f0bcb7b6cd7b3a0e9fa Mon Sep 17 00:00:00 2001 From: Matt Brubeck Date: Mon, 2 Nov 2015 11:21:30 -0800 Subject: [PATCH] Docs: Clarify what `cargo test` compiles vs. runs --- src/doc/manifest.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/doc/manifest.md b/src/doc/manifest.md index c00f33c02..d30001fef 100644 --- a/src/doc/manifest.md +++ b/src/doc/manifest.md @@ -424,11 +424,11 @@ your tests to protect them from bitrotting. When you run `cargo test`, Cargo will: -* Compile your library's unit tests, which are in files reachable from +* Compile and run your library's unit tests, which are in files reachable from `lib.rs`. Any sections marked with `#[cfg(test)]` will be included. -* Compile your library’s documentation tests, which are embedded inside - of documentation blocks. -* Compile your library's integration tests, which are located in +* Compile and run your library’s documentation tests, which are embedded + inside of documentation blocks. +* Compile and run your library's integration tests, which are located in `tests`. Files in `tests` load in your library by using `extern crate ` like any other code that depends on it. * Compile your library's examples. -- 2.30.2